CVE-2023-54015
net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device
Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device In case devcom allocation is failed, mlx5 is always freeing the priv. However, this priv might have been allocated by a different thread, and freeing it might lead to use-after-free bugs. Fix it by freeing the priv only in case it was allocated by the running thread.
INFO
Published Date :
Dec. 24, 2025, 11:15 a.m.
Last Modified :
Dec. 24, 2025, 11:15 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2023-54015
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Review allocation and free logic for thread safety.
- Modify code to check thread ownership before freeing.
- Apply the latest kernel patches for mlx5 driver.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-54015.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-54015 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-54015
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-54015 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-54015 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Dec. 24, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device In case devcom allocation is failed, mlx5 is always freeing the priv. However, this priv might have been allocated by a different thread, and freeing it might lead to use-after-free bugs. Fix it by freeing the priv only in case it was allocated by the running thread. Added Reference https://git.kernel.org/stable/c/1e755065368000205e6683fa924b2654e99f573b Added Reference https://git.kernel.org/stable/c/3dfc1004d9afbf689087ae1eafd88f55481984c7 Added Reference https://git.kernel.org/stable/c/a3a516caef2c5be2f4d171890a8b3415bfab4e5e Added Reference https://git.kernel.org/stable/c/af87194352cad882d787d06fb7efa714acd95427 Added Reference https://git.kernel.org/stable/c/d4d10a6df1529b3f446cdada5c25e065f4712756 Added Reference https://git.kernel.org/stable/c/eaa365c10459052cbe3e44caa4ad760cb93bd435